Communication to one mobile station of update of call participation availability status of another mobile station

ABSTRACT

An application server component of an apparatus in one example communicates to one or more mobile stations, of a plurality of mobile stations, one or more updates of one or more statuses of respective one or more mobile stations of the plurality of mobile stations. The plurality of mobile stations comprise a first mobile station and a second mobile station, wherein the one or more updates of the one or more statuses of the respective one or more mobile stations comprise an update of a status of the first mobile station. The application server component communicates the update of the status of the first mobile station to the second mobile station to indicate to the second mobile station whether the first mobile station is available for participation in a call with the second mobile station.

TECHNICAL FIELD

[0001] The invention relates generally to communications and moreparticularly to availability status of mobile stations.

BACKGROUND

[0002] It is desirable for a user of a mobile station to know theavailability of other users of mobile stations before attempting tocommunicate with the other users. If the user knows the availabilitystatuses of the other users, then the user may avoid wasting time andresources by foregoing attempts to communicate with the other usersduring times that the other users are unavailable.

[0003] Some personal computers employ a software application, forexample, a real-time availability status presentation application, forexample, AOL® Instant Messenger™ service offered by America Online, Inc.(New York, N.Y. 10019, http://www.aol.com), to notify a user of thepersonal computer of the status of other users in a network. If the usersubscribes to the Instant Messenger™ service, then the user mayestablish a list, for example, a buddy list, of the other users who havealso subscribed to the Instant Messenger™ service. The InstantMessenger™ service monitors the availability status of the other userson the user's buddy list and provides to the user real-time availabilitystatus updates about the other users. When one of the other users signsonto the Instant Messenger™ service, for example, the Instant Messenger™service communicates an update of the status of that other user, forexample, from “not logged on” to “logged on.” The update notifies theoriginal user that the other user is available for communication.

[0004] One shortcoming of the arrangement is that the real-timeavailability status presentation application is not available for theuser of the mobile station to monitor the status of the other users. Forexample, a first user must attempt communication with a second user todetermine an availability of the second user. If the first user attemptscommunication with the second user and the second user is unavailable,then the first user has wasted time and resources by attemptingcommunication with the second user. Without knowledge of theavailability of the second user, the first user is unable to distinguishbetween different causes for the unavailability of the second user. Forexample, the second user may be currently engaged in a call, poweredoff, unavailable, or not accepting calls. Without being able todistinguish between the different causes of the unavailability of thesecond user, the first user may make subsequent calls to the second userand continue to waste time and resources.

[0005] Thus, a need exists for enhanced information about the callstatus availability of mobile stations.

SUMMARY

[0006] The invention in one embodiment encompasses an apparatus. Theapparatus comprises an application server component that communicates toone or more mobile stations, of a plurality of mobile stations, one ormore updates of one or more statuses of respective one or more mobilestations of the plurality of mobile stations. The plurality of mobilestations comprise a first mobile station and a second mobile station,wherein the one or more updates of the one or more statuses of therespective one or more mobile stations comprise an update of a status ofthe first mobile station. The application server component communicatesthe update of the status of the first mobile station to the secondmobile station to indicate to the second mobile station whether thefirst mobile station is available for participation in a call with thesecond mobile station.

[0007] Another embodiment of the invention encompasses a method. One ormore statuses of respective one or more mobile telephones of a pluralityof mobile telephones are monitored. The plurality of mobile telephonescomprise a first mobile telephone and a second mobile telephone. Anupdate of a status, of the one or more statuses, of the second mobiletelephone is communicated to the first mobile telephone.

[0008] Yet another embodiment of the invention encompasses an article.The article comprises one or more computer-readable signal-bearingmedia. The article comprises means in the one or more media formonitoring one or more statuses of respective one or more mobiletelephones of a plurality of mobile telephones. The plurality of mobiletelephones comprise a first mobile telephone and a second mobiletelephone. The article comprises means in the one or more media forcommunicating to the first mobile telephone an update of a status, ofthe one or more statuses, of the second mobile telephone.

DESCRIPTION OF THE DRAWINGS

[0009] Features of exemplary implementations of the invention willbecome apparent from the description, the claims, and the accompanyingdrawings in which:

[0010]FIG. 1 is a representation of an exemplary implementation of anapparatus that comprises one or more application server components, oneor more networks, one or more databases, one or more session controlcomponents, one or more data nodes, one or more media resource functioncomponents, and a plurality of mobile stations.

[0011]FIG. 2 is a representation of one exemplary message flow betweentwo of the mobile stations for a registration of one of the mobilestations and notification of a change in a status of one of the mobilestations of the apparatus of FIG. 1.

[0012]FIG. 3 is a representation of one exemplary message flow for abuddy list conference between two of the mobile stations of theapparatus of FIG. 1.

[0013]FIG. 4 is a representation of another exemplary message flowbetween two of the mobile stations for a registration of one of themobile stations and notification of a change in a status of one of themobile stations of the apparatus of FIG. 1.

[0014]FIG. 5 is a representation of another exemplary message flow for abuddy list conference between two of the mobile stations of theapparatus of FIG. 1.

DETAILED DESCRIPTION

[0015] Turning to FIG. 1, an apparatus 100 in one example comprises aplurality of components such as computer software and/or hardwarecomponents. A number of such components can be combined or divided inthe apparatus 100.

[0016] The apparatus 100 in one example comprises one or moreapplication server (“AS”) components 102, one or more networks 104, oneor more databases (“DBs”) 106, one or more session control components(“SCC”) 108, one or more data nodes (“DNs”) 110, one or more mediaresource function (“MRF”) components 111, and a plurality of mobilestations (“MSs”) 112, 114, and 116. The mobile stations 112, 114, and116 in one example are operable by one or more users. The users of themobile stations 112, 114, and 116 in one example comprise humanoperators. The application server component 102, the session controlcomponent 108, the database 106, the data node 110, and the mediaresource function component 111 in one example comprise computercomponents, for example, computer software and/or hardware components.The network 104, the database 106, the session control component 108,the data node 110, and the media resource function component 111 in oneexample comprise telecommunications network components.

[0017] For example, the apparatus 100 comprises a buddy list servicethat monitors a status (e.g., online, offline, busy, on a call) of themobile stations 112, 114, and 116 to determine whether the mobilestations 112, 114, and 116 are available for participation in a call. Abuddy list in one example comprises a user administered list ofcolleagues, workgroup members, and/or friends (e.g., the mobile stations112, 114, and 116) that one of the mobile stations 112, 114, and 116wishes to monitor via the buddy list service. The call for whichavailability of the mobile stations 112, 114, or 116 is determined inone example comprises one or more of voice communication, datacommunication, and messaging.

[0018] In one example, the application server component 102 serves tocontrol a notification of the status of the mobile stations 112, 114,and 116 to one or more other of the mobile stations 112, 114, and 116.For example, the user of the mobile stations 112 is a subscriber to thebuddy list service and administers a buddy list that comprisesindications of the mobile stations 114 and 116. Upon registration of themobile station 112 with the network 104, the application servercomponent 102 returns the status of each member (e.g., the status of themobile stations 114 and 116) of the buddy list to the mobile station112.

[0019] In a further example, the application server component 102 servesto control a notification of a change in status of one of the mobilestations 112, 114, and 116 to the one or more other of the mobilestations 112, 114, and 116. For example, upon a change in the status ofthe mobile station 114, the application server component 102 sends anotification message to the mobile station 112. The application servercomponent 102 sends analogous notification messages to other mobilestations (e.g., the mobile station 116) that have a buddy list thatcomprises an indication of the mobile station 114.

[0020] The network 104 and/or the mobile stations 112, 114, and 116 sendone or more status update messages to the application server component102 upon a change in the status of the one of the mobile stations 112,114, and 116. The application server component 102 processes the one ormore status update messages and determines which of the mobile stations112, 114, and 116 should be notified of the change in the status of theone of the mobile stations 112, 114, and 116.

[0021] During a connection of a call from an originating mobile stationof the mobile stations 112, 114, and 116 to a receiving mobile stationof the mobile stations 112, 114, and 116 the originating mobile stationsends a call request to the session control component 108. The call inone example comprises one or more of voice communication, datacommunication, and messaging. The session control component 108 passesthe call request to the application sever component 102. The callrequest comprises an indication of one or more buddies of the buddy listof the originating mobile station. The application sever component 102in one example may perform name-to-number resolution. For example,application sever component 102 performs a translation from anindication of the one or more buddies to an E.164 number. The E.164number may comprise one or more of a phone number (e.g., 1-312-346-2800)and a Universal Resource Locator (“URL”) (e.g.,http://www.pattibrill.com). In one example, referring to FIG. 1, theapplication sever component 102 resides within the network 104. Inanother example, the application sever component 102 is external to thenetwork 104 and communicates with the network 104 through an externalcommunication path (not shown), as will be appreciated by those skilledin the art.

[0022] The network 104 in one example serves to provide a medium totransmit messages between the application server component 102, thedatabase 106, the session control component 108, the data node 110, themedia resource function component 111, and the mobile stations 112, 114,and 116. The network 104 in one example comprises a plurality of networkdevices such as routers, switches, and servers.

[0023] The database 106 in one example serves to store subscriberprofiles of the one or more users of the mobile stations 112, 114, and116. The database 106 comprises a home location register (“HLR”). Thedatabase 106 processes one or more user profile query messages from thesession control component 108. Upon receipt of one of the user profilequery messages from the session control component 108, the database 106returns the user profile that corresponds to the user requested by thesession control component 108. The user profile comprises informationregarding services available to the user (e.g., permissions, buddy listservice subscription information, conference call services, voice mail,data and voice communications) and information regarding routing ofmessages to the application server component 102.

[0024] The database 106 in one example comprises a first list 120 and asecond list 122. In another example, the mobile station 112 stores thefirst list 120 and the second list 122. In one example, the first list120 comprises a subscription list (e.g., the buddy list) for the user ofthe mobile station 112. The first list 120 identifies one or more of themobile stations 114 and 116 from/about which the user of the mobilestation 112 requests to receive status updates. The first list 120comprises one or more groups. For example, the groups of the first list120 may comprise one or more of a work group, a social group, and familygroup. In one example, the second list 122 comprises areverse-subscription list (e.g., a reverse-buddy list) for the user ofthe mobile station 112. The second list 122 comprises a list of theusers of the mobile stations 114 and 116 which list as a buddy the userof the mobile stations 112. The second list 122 identifies one or moreof the mobile stations 114 and 116 that request to receive statusupdates from/about the mobile station 112.

[0025] The session control component 108 in one example serves as a callcontrol function, for example, a call state control function (“CSCF”),component. The session control component 108 may establish a callbetween the mobile stations 112, 114, and 116. For example, the sessioncontrol component 108 monitors the status of one or more of the mobilestations 112, 114, and 116 and notifies the application server component102 upon a change in the status of at least one of the monitored mobilestations 112, 114, and/or 116.

[0026] In one example, the data node 110 serves to receive and processmessages from the application server component 102. In a furtherexample, the data node 110 serves to notify one of the mobile stations112, 114, and 116 of a change in the status of another of the mobilestations 112, 114, and 116. The data node 110 comprises one or more of aServing General Packet Radio Service (“GPRS”) Support Node (“SGSN”), aGateway GPRS Support Node (“GGSN”), a Packet Data Serving Node (“PDSN”),a short message service center (“SMSC”), and the call state controlfunction component. For example, the data node 110 comprises a subpartof the session control component 108. The media resource functioncomponent 111 serves to generate announcements, play tones, and manageconference services.

[0027] The mobile stations 112, 114, and 116 in one example serve toinitiate a change in the status of the mobile stations 112, 114, and116. One of the mobile stations 112, 114, and 116 in one example servesto initiate a call to another of the mobile stations 112, 114, and 116.The mobile stations 112, 114, and 116 communicate via the network 104.For example, the mobile stations 112, 114, and 116 engage in mobiletelephone communication (e.g., calls, voice mail, and short messagingservices, “SMS,” via the network 104. The mobile stations 112, 114, and116 in one example comprise one or more of handheld devices, mobiletelephones, cellular phones, mobile computers, and personal digitalassistants (“PDAs”).

[0028] In one example, the user of the mobile station 112 employs a menuto initiate a call to one or more of the mobile stations 114 and 116. Inanother example, the user of the mobile station 112 employs the menu toindicate a change in status of the mobile station 112. For example, theuser of the mobile station 112 changes the status of the mobile station112 from an available status to a busy status. To initiate the change instatus, the user of the mobile station 112 selects a set-busy statusfunction from the menu. In one example, the mobile station 112 notifiesthe session control component 108 of the change in status (e.g., whenthe first list 120 and the second list 122 reside in the database 106).In another example, the mobile station 112 notifies the applicationserver component 102 of the change in status (e.g., when the first list120 and the second list 122 reside in the mobile station 112).

[0029] Turning to FIG. 2, one illustrative description of exemplaryoperation of the apparatus 100 is presented, for explanatory purposes. Amessage flow 201 represents exemplary registration of the mobile station112 and notification of a change in a status of the mobile station 112based on the registration. The message flow 201 illustrates one examplewhere the user administered buddy lists of the mobile stations 112, 114,and 116 are stored in the network 104.

[0030] In one example, the user of the mobile station 112 employs anautomatic mobile-based update functionality to register the mobilestation 112 with the network 104. The mobile station 112 sends aregistration message 202 to the session control component 108.“REGISTRATION” in one example serves to represent the registrationmessage 202. The message flow 201 illustrates the registration of themobile station but is easily extendable to handle call origination orpage answering by substituting an originate call or a answer pagemessage for the registration message 202.

[0031] In another example, the user of the mobile station 112 employs amanual mobile-based update functionality to provide the status of themobile station 112 to the network 104. The user initiates the manualmobile-based update functionality by interacting with the mobile station112, for example, by pressing a button 140 (FIG. 1) on the mobilestation 112. The button 140 in one example comprises a status-changecomponent. The mobile station 112 sends a change in status message 204to the session control component 108. “UE CHANGE” in one example servesto represent the change in status message 204.

[0032] Upon receipt of either of the registration message 202 or thechange in status message 204, the session control component 108 sends aquery message 206 to the database 106. “QUERY (USER)” in one exampleserves to represent the query message 206. “USER” in one example servesto represent an indication of the mobile station 112. The query message206 initiates a download of a profile of the user of the mobile station112 from the database 106. Upon receipt of the query message 206, thedatabase 106 in one example sends a response message 208 to the sessioncontrol component 108. “RESP (PROFILE)” in one example serves torepresent the response message 208. “PROFILE” in one example serves torepresent an indication of the profile of the user of the mobile station112. The profile of the user of the mobile station 112 in one examplecomprises buddy list service information of the mobile station 112.

[0033] Upon receipt of the response message 208, the session controlcomponent 108 in one example determines whether the user of the mobilestation 112 is subscribed to the buddy list service. If the user of themobile station 112 is subscribed to the buddy list service, then thesession control component 108 in one example sends a notificationmessage 210 to the application server component 102. “REG-NOTIFY (USER,STATUS)” in one example serves to represent the notification message210. “USER” in one example serves to represent an indication of themobile station 112. “STATUS” in one example serves to represent anindication of the status of the mobile station 112. The notificationmessage 210 informs the application server component 102 of the statusof the mobile station 112. Upon receipt of the notification message 210,the application server component 102 in one example sends anacknowledgement 212 to the session control component 108.

[0034] The application server component 102 in one example sends a buddylist update message 214 to the data node 110. “UPDATE MS (BUDDIES,STATUS)” in one example serves to represent the buddy list updatemessage 214. “BUDDIES” in one example serves to represent an indicationof one or more of the mobile stations 114 and 116 on the buddy list ofthe user of the mobile station 112. “STATUS” in one example serves torepresent an indication of the status of the one or more of the mobilestations 114 and 116 on the buddy list of the user of the mobile station112. The buddy list update message 214 in one example provides themobile station 112 with the status of the one or more of the mobilestations 114 and 116 on the buddy list of the user of the mobile station112. The data node 110 forwards the buddy list update message 214 to themobile station 112. Upon receipt of the response message 214, the mobilestation 112 in one example sends an acknowledgement 216 to the data node110. The data node 110 in one example forwards the acknowledgement 216to the application server component 102.

[0035] Upon receipt of the acknowledgement 216, the application servercomponent 102 in one example sends a notification message 218 to thedata node 110. “NOTIFY (BUDDIES, USER, STATUS)” in one example serves torepresent the notification message 218. “BUDDIES” in one example servesto represent an indication of one or more of the mobile stations 114 and116 that comprise buddy lists that contain an indication of the mobilestation 112. “USER” in one example serves to represent the indication ofthe mobile station 112. “STATUS” in one example serves to represent anindication of the status of the mobile station 112 (e.g., online,offline, busy, on a call). The notification message 218 provides the oneor more of the mobile stations 114 and 116 with the status of the mobilestation 112. The mobile station 114 in one example comprises a buddylist that contains an indication of the mobile station 112. Therefore,the data node 110 in one example forwards the notification message 218to the mobile station 114. Upon receipt of the notification message 218,the mobile station 114 in one example sends an acknowledgement 220 tothe data node 110. The data node 110 in one example forwards theacknowledgement 220 to the application server component 102. Theapplication server component 102 in one example replicates and sends thenotification message 218 to other mobile stations that comprise a buddylist that contains the indication of the mobile station 112.

[0036] Turning to FIG. 3, another illustrative description of exemplaryoperation of the apparatus 100 is presented, for explanatory purposes. Amessage flow 301 represents an exemplary buddy list conference betweenthe mobile station 112 and one or more members of the buddy list (e.g.,the mobile station 114). The message flow 301 also represents anotification of a change in the status of the mobile station 112 and theone or more members of the buddy list based on the buddy listconference. The message flow 301 illustrates one example where the useradministered buddy lists of the mobile stations 112, 114, and 116 arestored in the network 104.

[0037] The user of the mobile station 112 in one example sends buddylist conference request message 302 to the session control component108. “VOICE CALL (BUDDY LIST)” in one example serves to represent thebuddy list conference request message 302. “BUDDY LIST” in one exampleserves to represent an indication of one or more members of the buddylist that the user of the mobile station 112 includes in the buddy listconference.

[0038] Upon receipt of the buddy list conference request message 302,the session control component 108 in one example sends a query message206 to the database 106. “QUERY (USER)” in one example serves torepresent the query message 206. “USER” in one example serves torepresent an indication of the mobile station 112. The query message 206in one example initiates a download of the profile of the user of themobile station 112 from the database 106. Upon receipt of the querymessage 206, the database 106 in one example sends a response message208 to the session control component 108. “RESP (PROFILE)” in oneexample serves to represent the response message 208. “PROFILE” in oneexample serves to represent an indication of the profile of the user ofthe mobile station 112.

[0039] Upon receipt of the response message 208, the session controlcomponent 108 in one example determines whether the user of the mobilestation 112 is subscribed to the buddy list service. If the user of themobile station 112 is subscribed to the buddy list service, then thesession control component 108 in one example sends a buddy listconference setup message 304 to the application server component 102.“CALL BUDDY (USER, BUDDY LIST)” in one example serves to represent thebuddy list conference setup message 304. “USER” in one example serves torepresent an indication of the mobile station 112. “BUDDY LIST” in oneexample serves to represent an indication of one or more members of thebuddy list that the user of the mobile station 112 includes in the buddylist conference.

[0040] Upon receipt of the buddy list conference setup message 304, theapplication server component 102 in one example performs thename-to-number resolution and sends a response message 306 to thesession control component 108. “CALL BUDDY (TERMINATION LIST)” in oneexample serves to represent the response message 306. “TERMINATION LIST”in one example serves to represent an indication of connectioninformation (e.g., a telephone number or an internet protocol, “IP,”address) of the one or more members of the buddy list that the user ofthe mobile station 112 includes in the buddy list conference.

[0041] Upon receipt of the response message 306, the session controlcomponent 108 in one example sends a setup message 308 to the mediaresource function component 111. “ESTABLISH CALL TO BUDDIES” in oneexample serves to represent the setup message 308. Upon receipt of thesetup message 308, the media resource function component 111 in oneexample sends a connect message 310 to the mobile station 112 and theone or more members of the buddy list that the user of the mobilestation 112 included in the buddy list conference. The media resourcefunction component 111 in one example sends the connect message 310 tothe mobile station 112 and the mobile station 114 to initiatecommunication between the mobile station 112 and the mobile station 114.

[0042] Once communication begins between the mobile station 112 and themobile station 114, the application server component 102 in one examplesends a notification message 312 to the data node 110. “NOTIFY (USER,BUDDY LIST, STATUS)” in one example serves to represent the notificationmessage 312. “BUDDIES” in one example serves to represent an indicationof one or more of the mobile stations 112, 114, and 116 that have buddylists that contain an indication of the mobile station 112 or the mobilestation 114. “USER” in one example serves to represent the indication ofthe mobile station 112 and the mobile station 114. “STATUS” in oneexample serves to represent an indication of the status of the mobilestation 112 and the mobile station 114. Upon receipt of the notificationmessage 312, the data node 110 in one example forwards the notificationmessage 312 to the one or more of the mobile stations 112, 114, and 116that comprise buddy lists that contain an indication of the mobilestation 112 or the mobile station 114. The notification message 312 inone example alerts the one or more of the mobile stations 112, 114, and116, which comprise buddy lists that contain an indication of the mobilestation 112 or the mobile station 114, that the mobile station 112 andthe mobile station 114 are on a call.

[0043] The communication between the mobile station 112 and the mobilestation 114 in one example continues until the mobile station 112 or themobile station 114 ends the communication. To end the communication withthe mobile station 114, the mobile station 112 in one example sends anend communication message 314 to the session control component 108. “ENDCALL (MS)” in one example serves to represent the end communicationmessage 314. Upon receipt of the end communication message 314, thesession control component 108 in one example forwards the endcommunication message 314 to the application server component 102.

[0044] Upon receipt of the end communication message 314, theapplication server component 102 in one example sends a response message316 to the session control component 108. “END CALL (TERMINATION LIST)”in one example serves to represent the response message 316.“TERMINATION LIST” in one example serves to represent an indication ofconnection information of the one or more members of the buddy list thatthe user of the mobile station 112 includes in the buddy listconference.

[0045] Upon receipt of the response message 316, the session controlcomponent 108 in one example sends an end buddy list conference message318 to the media resource function component 111. “REMOVE CONF (MS)” inone example serves to represent the end buddy list conference message318. The session control component 108 in one example also sends an endcall message 320 to the one or more members of the buddy list that areinvolved in the buddy list conference.

[0046] Once communication ends between the mobile station 112 and themobile station 114, the application server component 102 in one examplesends a notification message 322 to the data node 110. “NOTIFY (USER,BUDDY LIST, STATUS)” in one example serves to represent the notificationmessage 322. “USER” in one example serves to represent the indication ofthe mobile station 112 and the mobile station 114. “BUDDY LIST” in oneexample serves to represent an indication of one or more of the mobilestations 112, 114, and 116 that comprise buddy lists that contain anindication of the mobile station 112 and/or the mobile station 114.“STATUS” in one example serves to represent an indication of the statusof the mobile station 112 and the mobile station 114. Upon receipt ofthe notification message 322, the data node 110 in one example forwardsthe notification message 322 to the one or more of the mobile stations112, 114, and 116 that comprise buddy lists that contain the indicationof the mobile station 112 and/or the mobile station 114. Thenotification message 322 in one example alerts the one or more of themobile stations 112, 114, and 116, which have buddy lists that containthe indication of the mobile station 112 and/or the mobile station 114,that the mobile station 112 and the mobile station 114 are available fora call.

[0047] Turning to FIG. 4, a further illustrative description ofexemplary operation of the apparatus 100 is presented, for explanatorypurposes. A message flow 401 represents an exemplary registration of themobile station 112 and notification of a change in the status of themobile station 112 based on the registration. The message flow 401illustrates one example where the user administered buddy lists of themobile stations 112, 114, and 116 are stored in the respective mobilestations 112, 114, and 116.

[0048] The user of the mobile station 112 in one example employs one ofthe automatic mobile-based update functionality (e.g., the registrationmessage 202) or the manual mobile-based update functionality (e.g.,status message 204) to provide the status of the mobile station 112 tothe network 104, where the message flow 401 is at least in partanalogous to the message flow 201. The user administered buddy list ofthe mobile station 112 is stored in the mobile station 112, thereforethe session control component 108 in one example does not check theprofile of the mobile station 112 for buddy list service subscriptions,where the message flow 401 at least in part differs from the messageflows 201 and 301. The mobile station 112 in one example sends anotification message 402 to the application server component 102.“REG-NOTIFY (USER, STATUS)” in one example serves to represent thenotification message 402. The notification message 402 in one exampleinforms the application server component 102 of the status of the mobilestation 112.

[0049] Upon receipt of the notification message 402, the applicationserver component 102 in one example sends an acknowledgement 404 to themobile station 112. The application server component 102 in one examplealso sends a buddy list update message 406 to the data node 110. “UPDATEMS (BUDDIES, STATUS)” in one example serves to represent the buddy listupdate message 406. The buddy list update message 406 in one exampleprovides the mobile station 112 with the status of the one or more ofthe mobile stations 114 and 116 on the buddy list of the user of themobile station 112. The data node 110 in one example forwards the buddylist update message 406 to the mobile station 112. Upon receipt of theresponse message 406, the mobile station 112 in one example sends anacknowledgement 408 to the data node 110. The data node 110 in oneexample forwards the acknowledgement 408 to the application servercomponent 102.

[0050] Upon receipt of the acknowledgement 408, the application servercomponent 102 in one example sends a notification message 410 to thedata node 110. “NOTIFY (BUDDIES, USER, STATUS)” in one example serves torepresent the notification message 410. The notification message 218 inone example provides the one or more of the mobile stations 114 and 116with the status (e.g., online, offline, busy, on a call, etc.) of themobile station 112. The mobile station 114 in one example comprises abuddy list that contains an indication of the mobile station 112.Therefore, the data node 110 in one example forwards the notificationmessage 410 to the mobile station 114. Upon receipt of the notificationmessage 410, the mobile station 114 in one example sends anacknowledgement 412 to the data node 110. The data node 110 in oneexample forwards the acknowledgement 412 to the application servercomponent 102. The application server component 102 in one examplereplicates and sends the notification message 410 to any other mobilestation that comprises a buddy list that contains the indication of themobile station 112.

[0051] Turning to FIG. 5, a still further illustrative description ofexemplary operation of the apparatus 100 is presented, for explanatorypurposes. A message flow 501 represents an exemplary buddy listconference between the mobile station 112 and one or more members of thebuddy list (e.g., the mobile station 114). The message flow 501 alsorepresents a notification of a change in the status of the mobilestation 112 and the one or more members of the buddy list based on thebuddy list conference. The message flow 501 illustrates one examplewhere the user administered buddy lists of the mobile stations 112, 114,and 116 reside in the respective mobile stations 112, 114, and 116.

[0052] The message flow 501 in one example is substantially analogous tothe message flow 301. One difference between the message flow 501 andthe message flow 301 is the user administered buddy lists of the mobilestations 112 reside within the mobile stations 112. Therefore, ratherthan checking the database 106 and the session control component 108 forthe user administered buddy lists of the mobile stations 112, the userof the mobile station 112 in one example sends a buddy list conferencesetup message 502 to the application server component 102. “CALL BUDDY(USER, BUDDY LIST)” in one example serves to represent the buddy listconference setup message 502. “USER” in one example serves to representan indication of the mobile station 112. “BUDDY LIST” in one exampleserves to represent an indication of one or more members of the buddylist that the user of the mobile station 112 includes in the buddy listconference. Beginning sequentially with the response message 306 andending with the notification message 322, the remainder of the messageflow 501 in one example is analogous to the message flow 301.

[0053] The apparatus 100 in one example employs one or morecomputer-readable signal-bearing media. One example of acomputer-readable signal-bearing medium for the apparatus 100 comprisesan instance of a recordable data storage medium 101 such as one or moreof a magnetic, electrical, optical, biological, and atomic data storagemedium. In another example, a computer-readable signal-bearing mediumfor the apparatus 100 comprises a modulated carrier signal transmittedover a network comprising or coupled with the apparatus 100, forinstance, one or more of a telephone network, a local area network(“LAN”), the internet, and a wireless network. An exemplary component ofthe apparatus 100 employs and/or comprises a set and/or series ofcomputer instructions written in or implemented with any of a number ofprogramming languages, as will be appreciated by those skilled in theart.

[0054] The steps or operations described herein are just exemplary.There may be many variations to these steps or operations withoutdeparting from the spirit of the invention. For instance, the steps maybe performed in a differing order, or steps may be added, deleted, ormodified.

[0055] Although exemplary implementations of the invention have beendepicted and described in detail herein, it will be apparent to thoseskilled in the relevant art that various modifications, additions,substitutions, and the like can be made without departing from thespirit of the invention and these are therefore considered to be withinthe scope of the invention as defined in the following claims.

We claim:
 1. An apparatus, comprising: an application server componentthat communicates to one or more mobile stations, of a plurality ofmobile stations, one or more updates of one or more statuses ofrespective one or more mobile stations of the plurality of mobilestations; wherein the plurality of mobile stations comprise a firstmobile station and a second mobile station, wherein the one or moreupdates of the one or more statuses of the respective one or more mobilestations comprise an update of a status of the first mobile station;wherein the application server component communicates the update of thestatus of the first mobile station to the second mobile station toindicate to the second mobile station whether the first mobile stationis available for participation in a call with the second mobile station.2. The apparatus of claim 1, wherein the update of the status of thefirst mobile station comprises a first update of the status of the firstmobile station; wherein the first mobile station comprises astatus-change component, wherein a user of the first mobile stationemploys the status-change component to communicate a change in thestatus of the first mobile station to the application server component;wherein based on the change in the status of the first mobile station,the application server component communicates a second update of thestatus of the first mobile station to the second mobile station.
 3. Theapparatus of claim 1, wherein the update of the status of the firstmobile station indicates to the second mobile station that the firstmobile station is available for participation in the call with thesecond mobile station, the apparatus further comprising: atelecommunications network component; wherein upon an involvement by thefirst mobile station in a call with a third mobile station of theplurality of mobile stations, the telecommunications network componentcommunicates to the application server component the involvement of thefirst mobile station in the call with the third mobile station.
 4. Theapparatus of claim 3, wherein the update of the status of the firstmobile station comprises a first update of the status of the firstmobile station, wherein the second mobile station comprises a buddy listthat is administered by a user of the second mobile station, wherein thebuddy list comprises an indication of the first mobile station; whereinthe one or more updates of the one or more statuses of the respectiveone or more mobile stations comprise a second update of the status ofthe first mobile station; wherein based on the involvement of the firstmobile station in the call with the third mobile station the applicationserver component communicates to the second mobile station the secondupdate of the status of the first mobile station; wherein the secondupdate of the status of the first mobile station indicates to the secondmobile station that the first mobile station is unavailable forparticipation in a call with the second mobile station.
 5. The apparatusof claim 4, wherein upon completion of the call with the third mobilestation, the telecommunications network component communicates to theapplication server component the completion of the call with the thirdmobile station; wherein the one or more updates of the one or morestatuses of the respective one or more mobile stations comprise a thirdupdate of the status of the first mobile station; wherein based on thecompletion of the call with the third mobile station the applicationserver component communicates to the second mobile station the thirdupdate of the status of the first mobile station; wherein the thirdupdate of the status of the first mobile station indicates to the secondmobile station that the first mobile station is available forparticipation in a call with the second mobile station.
 6. The apparatusof claim 1, wherein the second mobile station comprises a buddy listthat is administered by a user of the second mobile station, wherein thebuddy list comprises an indication of the first mobile station; whereinthe application server component employs the buddy list to monitor thestatus of the first mobile station; wherein the application servercomponent employs the buddy list to generate the update of the status ofthe first mobile station.
 7. The apparatus of claim 1, wherein the firstmobile station notifies the application server component upon a changein the status of the first mobile station.
 8. The apparatus of claim 1,further comprising: a telecommunications network component, wherein theapplication server component communicates the update of the status ofthe first mobile station to the second mobile station through thetelecommunications network component.
 9. The apparatus of claim 8,wherein the telecommunications network component notifies theapplication server component upon a change in the status of the firstmobile station.
 10. The apparatus of claim 8, wherein thetelecommunications network component comprises a user profile database,wherein the user profile database comprises a buddy list that isadministered by a user of the second mobile station, wherein the buddylist comprises an indication of the first mobile station; wherein theapplication server component employs the buddy list to monitor thestatus of the first mobile station; wherein the application servercomponent employs the buddy list to generate the update of the status ofthe first mobile station.
 11. The apparatus of claim 10, wherein thebuddy list comprises an indication of the first mobile station and oneor more additional mobile stations of the plurality of mobile stations,wherein the one or more updates of the one or more statuses of therespective one or more mobile stations comprise one or more updates ofone or more statuses of the one or more additional mobile stations,respectively; wherein the application server component employs the buddylist to monitor the one or more statuses of the one or more additionalmobile stations, respectively; wherein the application server componentemploys the buddy list to generate the one or more updates of the one ormore statuses of the one or more additional mobile stations,respectively.
 12. The apparatus of claim 8, wherein the call comprises afirst call, wherein the telecommunications network component comprises auser profile database, wherein the user profile database comprises areverse-buddy list of the second mobile station; wherein thereverse-buddy list comprises a list of one or more mobile stations ofthe plurality of mobile stations that administer a buddy list thatcomprises an indication of the second mobile station; wherein the one ormore updates of the one or more statuses of the respective one or moremobile stations comprise an update of a status of the second mobilestation; wherein the application server component communicates theupdate of the status of the second mobile station to the one or moremobile stations, that administer the buddy list that comprises theindication of the second mobile station, to indicate whether the firstmobile station is available for participation in a second call.
 13. Theapparatus of claim 8, wherein the telecommunications network componentcomprises a user profile database, wherein the user profile databasecomprises a buddy list that is administered by a user of the secondmobile station, wherein the buddy list comprises an indication of thefirst mobile station; wherein upon receipt by the application servercomponent of a call request from the second mobile station to the firstmobile station the application server component translates the callrequest from the indication of the first mobile station to a terminationaddress of the first mobile station.
 14. The apparatus of claim 8,wherein the telecommunications network component comprises a sessioncontrol component and a user profile database, wherein upon a change inthe status of the first mobile station, the session control componentretrieves a profile of the first mobile station from the user profiledatabase; wherein the session control component employs the profile todetermine permissions for the first mobile station.
 15. The apparatus ofclaim 1, wherein the plurality of mobile stations comprises a pluralityof mobile telephones, wherein the first mobile station comprises a firstmobile telephone of the plurality of mobile telephones, wherein thesecond mobile station comprises a second mobile telephone of theplurality of mobile telephones.
 16. The apparatus of claim 1, whereinthe call comprises any one or more of voice communication, datacommunication, and messaging.
 17. A method, comprising the steps of:monitoring one or more statuses of respective one or more mobiletelephones of a plurality of mobile telephones, wherein the plurality ofmobile telephones comprise a first mobile telephone and a second mobiletelephone; and communicating to the first mobile telephone an update ofa status, of the one or more statuses, of the second mobile telephone.18. The method of claim 17, wherein the step of monitoring the one ormore statuses of the respective one or more mobile telephones of theplurality of mobile telephones comprises the steps of: detecting by atelecommunications network component the one or more statuses of therespective one or more mobile telephones; and storing the one or morestatuses of the respective one or more mobile telephones in a userprofile database.
 19. The method of claim 17, wherein the step ofcommunicating to the first mobile telephone the update of the status ofthe second mobile telephone comprises the steps of: accessing a buddylist of the first mobile telephone that comprises an indication of theone or more mobile telephones; retrieving the one or more statuses ofthe respective one or more mobile telephones; and communicating to thefirst mobile telephone an update of the one or more statuses of therespective one or more mobile telephones.
 20. The method of claim 17,wherein the step of communicating to the first mobile telephone theupdate of the status of the second mobile telephone comprises the stepsof: receiving from the second mobile telephone an indication of a changein the status of the second mobile telephone; and sending the indicationto the first mobile telephone.
 21. The method of claim 20, furthercomprising the step of: sending the indication to one or more mobiletelephones of the plurality of mobile telephones that administer a buddylist that comprises an indication of the second mobile telephone. 22.The method of claim 17, further comprising the steps of: translating acall request made by the first mobile telephone to initiate a call witha third mobile telephone of the plurality of mobile telephones from anindication of the third mobile telephone to a termination address thatcorresponds to the third mobile telephone; and connecting the firstmobile telephone with the termination address for mobile communicationwith the third mobile telephone.
 23. The method of claim 17, wherein thestep of communicating to the first mobile telephone the update of thestatus of the second mobile telephone comprises the step of: notifying atelecommunications network component of a busy status of the secondmobile telephone to alert one or more mobile telephones of the pluralityof mobile telephones that the second mobile telephone is unavailable formobile communication.
 24. An article, comprising: one or morecomputer-readable signal-bearing media; means in the one or more mediafor monitoring one or more statuses of respective one or more mobiletelephones of a plurality of mobile telephones, wherein the plurality ofmobile telephones comprise a first mobile telephone and a second mobiletelephone; and means in the one or more media for communicating to thefirst mobile telephone an update of a status, of the one or morestatuses, of the second mobile telephone.